InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-04.Z/94-04/text0182.txt

Text File | 1994-04-30 | 12.7 KB | 282 lines

In article <[e-mail]> [e-mail] (Georg Schwarz) writes:
>From: [e-mail] (Georg Schwarz)
>Subject: Re: WFWG, ODI, MS TCP/IP AND ODIPKT!
>Date: Thu, 14 Apr 1994 14:29:11 UNDEFINED

>Just install your MTCPB1 with the NDIS2/NDIS3 drivers (no ODI stuff in WFW)
>and then add your ODI drivers manually in the AUTOEXEC. The winsock
>applications will use the NDIS drivers and your DOS program will use the
>TSR packet driver.

Using this configuration I can't  use the DOS clients  directly from windows I
have to quit it first. A better solution would be appreciated.

Thanks Georg
-------------------------------------------------------------------
Georg Schwarz              Institut fuer Geophysik
[e-mail]     ETH-Hoenggerberg
Voice: [phone]      CH-8093 Zuerich
Fax:   [phone]      Switzerland
-------------------------------------------------------------------
From [e-mail] Fri Apr 15 01:35:25 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA00462; Fri, 15 Apr 1994 08:39:22 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA32213; Thu, 14 Apr 1994 22:12:08 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Fri, 15 Apr 1994 01:35:25 GMT
From: [e-mail] (Bruce M. Walker)
Message-Id: <[e-mail]>
Organization: ISG Technologies Inc.
Sender: ses
Subject: Anybody get WLPRS40 to work over MS-TCP/IP March Beta?

I am running WFW 3.11 with MS-TCP/IP March Beta [there must be an
acronym for that; what about WfW311/MbTCP?].

I tried to get WLPR v4.0 to work with this, and it can do a queue query
(ie: equivalent to "lpq -Pps"), but it refuses to send the job.  I
enabled DLL debug mode and it looks OK until it tries to open a socket
(presumably to the remote lpd), then it returns a socket error and
disables the queue.

Luckily I still have WLPRS30, and that works OK, although the
installation is klugey.

So, has it worked for anyone else?

--
[e-mail]   [ ...!uunet.ca!isgtec!bmw ]   Bruce Walker
From [e-mail] Fri Apr 15 01:10:43 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA00470; Fri, 15 Apr 1994 08:39:22 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA24584; Thu, 14 Apr 1994 22:01:14 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Fri, 15 Apr 1994 01:10:43 GMT
From: [e-mail] (Bruce M. Walker)
Message-Id: <[e-mail]>
Organization: ISG Technologies Inc.
Sender: ses
References: <[e-mail]>, <[e-mail]>, <[e-mail]>
Subject: Re: WFW TCP/IP Mar Beta: really slow FTP?

[ Note: followup-to comp.os.ms-windows.networking.windows ]

In article <[e-mail]>,
Pete Bentley <[e-mail]> wrote:
>>>>>> In article <[e-mail]>, [e-mail] (Bob Daniel) writes:
>>> Hmm.. I get over 300K/s. Is your driver using Enhanced mode only or both
>>> Real and Enhanced?
>
>Hmm. Just noticed that my D-Link driver is only NDIS2.  Anyone know
>of an NDIS3 one? (I used to have a number for D-Link's BBS here in the
>UK, but I can't seem to find it...)
>
>Pete.

I'm using the 1992 NDIS2 driver that came with the D-Link DE600
adapter.  I assume that's real mode.  If somebody has the phone number
for the US (or Canada) D-Link BBS, I'd be glad to phone it up and see
if there's a newer driver available.  Unhappily, there are no phone
numbers or addresses or anything about support in the paperwork that
came with the D-Link adapter.  Talk about anonymous!

I have since tried running the March Beta MS-TCP over an Allied Telesis
AT1500T.  I get 130-150K bytes/sec FTPing vmunix (1.6Mbytes) from an
IPX to the crummy IDE drive on a 386sx.  So I'm not unhappy with the
basic product, just the particular instance of the DE600 thingy.

By the way, I used the Novel NE2100 NDIS3 and the NE1500 NDIS2 drivers
that came with MS-TCP, and the both yielded similar performance (as
above).  When I tried the Allied-Telesis driver from the WDL library,
the machine hung upon bootup!  (Actually, as soon as NET START runs.)

--
[e-mail]   [ ...!uunet.ca!isgtec!bmw ]   Bruce Walker
From [e-mail] Fri Apr 15 08:39:24 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA00479; Fri, 15 Apr 1994 08:39:24 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA12219; Thu, 14 Apr 1994 22:11:40 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 14 Apr 1994 14:29:11 UNDEFINED
From: [e-mail] (Georg Schwarz)
Message-Id: <[e-mail]>
Organization: ETH-Zuerich
Sender: ses
References: <hbae.766284510@cwis>
Subject: Re: WFWG, ODI, MS TCP/IP AND ODIPKT!

In article <hbae.766284510@cwis> [e-mail] (Hansang Bae) writes:
>From: [e-mail] (Hansang Bae)
>Subject: WFWG, ODI, MS TCP/IP AND ODIPKT!
>Date: Thu, 14 Apr 1994 00:48:30 GMT

>Ok, I have WFWG running fine with MS tcp/ip package.  I also use thier
>sockets and dnr program.  The only problem that I'm running into is that
>I cannot use ODIPKT.  I still have to use Clarkson's (Rutgers) DOS
>telnet.  Can't do it w/o ODIPKT.

>Actually, I can use odipkt fine, but if I load up ODINSUP (for ndis over
>odi), it crashes on me.  Has anyone gotten ODIPKT to coexit with
>ODINSUP?

Just install your MTCPB1 with the NDIS2/NDIS3 drivers (no ODI stuff in WFW)
and then add your ODI drivers manually in the AUTOEXEC. The winsock
applications will use the NDIS drivers and your DOS program will use the
TSR packet driver.

Hope this helps

Georg
-------------------------------------------------------------------
Georg Schwarz              Institut fuer Geophysik
[e-mail]     ETH-Hoenggerberg
Voice: [phone]      CH-8093 Zuerich
Fax:   [phone]      Switzerland
-------------------------------------------------------------------
From [e-mail] Fri Apr 11 13:21:23 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA00500; Fri, 15 Apr 1994 08:39:26 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA12263; Thu, 14 Apr 1994 22:12:31 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 11 Apr 94 13:21:23 GMT
From: [e-mail] (Ron Parise)
Message-Id: <2obisj$[e-mail]>
Organization: NASA Goddard Space Flight Center
Sender: ses
References: <[e-mail]>
Subject: Re: Is Chameleon Winsock in Windows Tour Guide book reccommended?

In article <[e-mail]>, [e-mail] (Zhahai Stewart) says:
>
>I've just started using winsock via a SLIP account.  Started with Trumpet
>winsock.  I have noticed that the book "Windows Internet Tour Guide" includes
>a trimmed set of clients along with a winsock from Chameleon.  Is there any
>advantage to switching to the Chameleon winsock from the book?  (And/or the
>clients in the book?).  I haven't bought the book yet, BTW; most of the book
>looks fairly elementary even to one of my lowly state of knowledge wrt the
>Internet.
>
>Are there any important limitations in the Chameleon Winsock included with the
>book?  (Beyond not having all the Chameleon clients included too)?
>     Thanks,  Z
>[e-mail]
>
The only limitation of the Chameleon package that comes with the book is
that is speaks only SLIP/PPP (there is no support for ethernet cards or any
other standard packet drivers. If you are using SLIP there is no particular
advantage to Chameleon over using Trumpet with it's built in slip support
(except that it is a little better at automatically establishing the link from
within windows).
If you are using PPP however, I have not found any reasonable packet
driver for PPP that I could make work with Trumpet, and Chameleon has PPP
support built in. This means that you can establish the connection from
within windows with a simple connection script instead of doing it manually
from dos, running the packet driver, running winpkt, and then running windows.
I am running Trumpet on this machine at work which has an ethernet
interface. And the free Chameleon package  home. Both
machines have the same compliment of winsock apps (mosaic, hgopher,
WS_FTP, timesync, xwin, serweb, telnet, wlprspool, wslpr, wnvnews,
..... etc......) and both work equally well.

I might mention that the pop mail client that comes with the Chameleon
sampler is very nice. I was using Eudora and have now switched to the
Chameleon package because it is truly multiuser. It allows a totally separate
configuration for each recipient (including the pop server address). At home
I have more than one person wanting to get mail on the system and each
gets their mail from a different server. I was not able to figure out any way
to get Eudora to have a separate pop server for each recipient (except to
completely switch .ini files for each person). The Chameleon has a login
window when you click on it and a totally independent configuration for
each recipient. Very nice!

Ron Parise
From [e-mail] Fri Apr 15 08:43:41 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01189; Fri, 15 Apr 1994 08:43:41 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA13364; Fri, 15 Apr 1994 05:46:12 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 14 Apr 1994 13:57:18
From: [e-mail] (David Sussman)
Message-Id: <[e-mail]>
Organization: Brown University
Sender: ses
Subject: FTP /SLIP   Save your ftp sites in the choices box ?

Is there a way to save your most frequently used ftp sites in the pull down
menu which has the original sites that ws_ftp intended you to connect to so I
don't have to keep typing my sites in.   Please email me back..   thanks :)
From [e-mail] Fri Apr 15 08:43:43 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01198; Fri, 15 Apr 1994 08:43:43 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA13376; Fri, 15 Apr 1994 04:46:32 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 14 Apr 1994 11:43:52
From: [e-mail] (Christopher King)
Message-Id: <[e-mail]>
Organization: ECC at Ford Motor Company, Dearborn Michigan
Sender: ses
References: <[e-mail]>
Subject: Re: Help with LAN Manager & Winsock

In article <[e-mail]> [e-mail] (Dean Zevchek) writes:
>From: [e-mail] (Dean Zevchek)
>Subject: Help with LAN Manager & Winsock
>Date: 11 Apr 1994 12:42 EST

>I just started looking into Windows Mosaic, Trumpet, Winsocks,
>etc, etc, and was wondering if anyone had any experience in
>getting Mosaic to run in a LAN Manager environment with pc's
>using Ungermann Bass network boards.

>From what I understand, besides the winsock 1.1 compliant DLL
>(trumpet or whatever) a packet driver specific to your network is
>needed.  The problem is that Ungermann Bass doesn't have one that
>I know of.  If I switch to Microsoft TCP I could probably get
>things to work but that involves ugly dual boot configurations
>and other problems.  Is there any sort of generic packet driver,
>or a way to kludge this?

>We are not fully NT yet (which I know works with Mosaic), so I'm
>specifically talking about users 386/486's running Windows 3.1.

>Any help would be appreciated,

>Dean Zevchek  -=>  [e-mail]


I would probably start with a call to UB, asking them if the network
adapter in question was NDIS-compliant (which I think would be a
prerequisite to using it with LAN Manager).  If it is, then there ought
to be a driver in existence for it (usually they just supply these to you
if you need them, according to the support docs I've read). Here, I've
been spoiled by applications packages that have all of the necessary
drivers included.

I suppose that, knowing the model # of the card, I could dig through
my stuff here to see if it may have been included somewhere... mabye
we could work something out.

C.K.